| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Marking a test with CONFIG+=insignificant_test will cause the exit code
of the test to be discarded during `make check'. This is intended to be
used for tests which are valuable to run, but are known to be unstable
and are not feasible to immediately fix.
Change-Id: Id7b2407d0a13c8de19a58badb78fa7c018c9b50a
Reviewed-by: Jo Asplin
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
doc/src/examples/wheel.qdoc
src/gui/util/qflickgesture.cpp
src/gui/util/qflickgesture_p.h
src/gui/util/qscroller.cpp
src/gui/util/qscroller.h
src/gui/util/qscroller_p.h
src/gui/util/qscrollerproperties.cpp
src/gui/util/qscrollerproperties.h
tests/auto/qscroller/tst_qscroller.cpp
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
tests/auto/qaccessibility/tst_qaccessibility.cpp
tests/auto/qsslsocket/tst_qsslsocket.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These assertions were made obsolete by the previous change to this test.
Change-Id: I3156b273a727f753a6c093c8fc7453b694c777ee
Task-number: QTBUG-17582
Reviewed-by: Rohan McGovern
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function generating data blocks was filling the block to 16 bytes
short of the blockSize, then appending three 8 byte values, causing the
block to grow 8 bytes beyond blockSize and then truncating it back to
blockSize.
This commit makes the code fill the block to 24 bytes short of the
blockSize, so that the block will always end up at the correct size and
truncation is not needed.
Change-Id: I9fe6e6d6cf7bc445513b53e0a910d205c4c8002f
Reviewed-by: Rohan McGovern
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| |/
|/|
| |
| |
| |
| |
| | |
Updated version of LGPL and FDL licenseheaders.
Apply release phase licenseheaders for all source files.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test machine is configured to pop up dialogs in case of CRT
assertion failures. The CRT has a debug assert whenever an invalid
file handle is used, while the test is expecting to get the EBADF
return code.
Due to some behaviour change in windows 7 (maybe SP1), we need to
call _CrtSetReportMode in addition to setting an error handler.
Reviewed-By: mread
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
examples/webkit/imageanalyzer/imageanalyzer.h
examples/webkit/imageanalyzer/mainwindow.h
mkspecs/unsupported/qws/linux-x86-openkode-g++/qplatformdefs.h
src/corelib/io/qfsfileengine_iterator_unix.cpp
src/corelib/io/qfsfileengine_iterator_win.cpp
src/corelib/kernel/qcoreapplication.cpp
src/network/access/qnetworkaccessdatabackend.cpp
src/plugins/bearer/connman/qconnmanservice_linux.cpp
src/plugins/platforms/openvglite/qwindowsurface_vglite.h
src/s60installs/bwins/QtCoreu.def
src/s60installs/eabi/QtCoreu.def
src/s60installs/s60installs.pro
tools/assistant/tools/assistant/helpviewer_qwv.h
tools/qdoc3/test/qt-html-templates.qdocconf
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test was using a FILE* after closing it (which was a pointer to
deleted memory). glibc detects and asserts on this.
If the test failed, then file could be closed twice too, so I fixed that
at the same time. (would have caused a double free)
Reviewed-by: joao
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix compile error for non symbian targets
Fix MSVCRT assertion failure
Test file.handle() returns the right thing before and after file is
closed.
Reviewed-by: joao
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Extended the existing tests which open a file from a handle to use
symbian RFile as well (when testing on symbian).
Added a new test to check the file handle is open/closed after closing
a QFile, based on whether the file was opened with AutoCloseHandle or
not.
Reviewed-by: mread
|
| | |
|
| |
| |
| |
| |
| | |
Mac's default file system is case-preserving, but case-insensitive,
otherwise.
|
| |
| |
| |
| |
| | |
If file system isn't case sensitive, open succeeds as should reading,
with the read data matching testData.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On symbian, check that opening files in protected locations either
succeeds or fails cleanly as expected by the capabilities the test is
compiled with.
This acts as a regression test for opening files in /resource, and also
checks the other locations behave as expected.
On all platforms, check file created with a mixed case filename
can be accessed by it's aliases that differ only in case (or not)
depending on the OS case sensitivity.
For Windows/Symbian, file should be accessible by altered case aliases
For other OS, it should not (other OS supported by Qt are unix like)
Reviewed-by: mread
|
| |
| |
| |
| |
| |
| | |
This was missed from the previous commit.
Reviewed-by: Joao
|
| |
| |
| |
| |
| |
| |
| | |
These tests have no GUI nor do they depend on network, so let's see what
breaks if they're parallelized :-)
Reviewed-by: Olivier Goffart
|
| |
| |
| |
| |
| |
| |
| | |
Absolute path for the link target can contain "../" elements and so
needs to be cleaned. Really depends on the definition for SRCDIR.
Reviewed-by: Prasanth Ullattil
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
demos/declarative/minehunt/minehunt.pro
src/corelib/io/io.pri
src/corelib/io/qfsfileengine.cpp
src/corelib/io/qfsfileengine_unix.cpp
src/corelib/io/qfsfileengine_win.cpp
src/s60installs/bwins/QtCoreu.def
src/s60installs/bwins/QtDeclarativeu.def
src/s60installs/bwins/QtGuiu.def
src/s60installs/eabi/QtCoreu.def
src/s60installs/eabi/QtDeclarativeu.def
src/s60installs/eabi/QtGuiu.def
tests/auto/qapplication/test/test.pro
tests/auto/qaudioinput/qaudioinput.pro
tests/auto/qaudiooutput/qaudiooutput.pro
tests/auto/qchar/qchar.pro
tests/auto/qdiriterator/qdiriterator.pro
tests/auto/qsound/qsound.pro
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Complement previous commit by aligning Qt itself to use .files
consistently for DEPLOYMENT as well as INSTALLS.
This excludes changes to webkit.
Task-number: QTBUG-3216
Reviewed-by: axis
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adding tests for these functions:
symLinkTarget / readLink (static & non static)
permissions (static)
constructors which take a QObject parent
After this, all function of QFile API are tested except encoding/decoding
functions and some QT3_SUPPORT inlines in the header.
Reviewed-by: joao
|
| |
| |
| |
| | |
Reviewed-By: joao
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Memory mapping of RFile handles is not supported in current symbian OS
versions. However the "open C" libraries provide an emulated mmap()
implementation which was used by QFile::map in Qt 4.6 release.
To avoid breaking applications which rely on this function, QFile::map
will now open the file with open C as well in order to use that handle
to call mmap().
When symbian implements a file mapping API, we can switch the implementation
to use that for RFile handles.
Reviewed-By: joao
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
File engine refactor caused a regression in the TIFF image codec,
as QFile::seek() previously worked like lseek() / fseek() in posix.
But on symbian the native RFile::Seek api clamps to the end of the file
if you attempt to seek beyond there.
This test checks seek behaviour in the appropriate place, the QFile
auto test.
Reviewed-By: joao
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Due to the change from default deployment in symbian from being hardcoded
in qmake to being in default_deployment.prf the .pro files needed to be
changed.
Specifically, "DEPLOYMENT = foo" needs to be "DEPLOYMENT += foo" otherwise
the default deployment lines are not added and the test won't install.
Reviewed-By: Miikka Heikkinen
|
| |
| |
| |
| |
| |
| |
| | |
Getting a posix file handle from a natively opened QFile isn't supported
so that part of the test is skipped.
Reviewed-By: joao
|
|/
|
|
| |
Reviewed-By: joao
|
|
|
|
|
|
|
|
|
|
| |
In Symbian each binary name must be unique as all binaries are stored
in the same directory on the device. Some autotests created helper
binaries that had same names on different tests, which caused
build and installation issues when building entire autotest project
tree.
Reviewed-by: Shane Kearns
|
| |
|
|
|
|
| |
this makes windows-style path specs *ugly*. that's intentional. :-P
|
|
|
|
|
|
|
|
|
|
| |
On this platform mmap'ing beyond EOF may succeed, even beyond filesystem
capabilities, but generate Bus Errors on access.
Skipping this failing test and accepting the underlying undefined
behavior is the right thing to do, until QFile offers proper guarantees.
Reviewed-by: Thiago Macieira
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
qmake/generators/symbian/symmake.cpp
src/gui/image/qimage.cpp
src/openvg/qwindowsurface_vgegl.cpp
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
... according to the online MSDN documentation.
Hid the cachedFd member in private data under WinCE, since it's never
used there.
Task-number: QTBUG-9085
Reviewed-by: Zeno Albisser
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When closing a file, the contents of the write buffer should be emptied
even in the case where flush fails, so it doesn't leak to subsequent
files opened through the same instance. This is inline with what would
happen with native close on a buffered device.
Also changed the resource file engine to succeed on flush. Since all
writes fail there, logically it's write buffer is empty and flush should
succeed. This keeps auto-tests happy :-)
tst_QFile::fullDisk auto-test extended to ensure re-opening QFile does
not keep the write buffer alive.
Reviewed-by: Thiago Macieira
|
|
|
|
|
|
|
|
|
| |
My patch from yesterday did not have any effect: Instead of
really using what was in the buffer, it used it but then read
it from the underlying device anyway.
Thanks Ritt Konstantin and Joao.
Reviewed-by: joao
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
| |
.. and more testcases
Reviewed-by: joao
|
|
|
|
|
|
|
|
| |
Some test very corrected, the low level file descriptor tests mostly
skipped as well as the multiple memory mapping of a file, which resulted
in the file handle not beeign properly released.
Reviewed-by: thartman
|
|
|
|
|
|
|
|
|
| |
The open() syscall can open directories for reading, which we
in QFile and file engines don't support. However, there is no need
for stat() to find out if it is a directory if we open() with a write
flag because then the syscall will fail anyway.
Reviewed-by: joao
|
|\
| |
| |
| |
| | |
Conflicts:
configure.exe
|
| |
| |
| |
| | |
RevBy: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chunk size increased to QIODEVICE_BUFFERSIZE (currently 16k) where
chunking is still needed. Namely, on sequential devices and when
QByteArray is unable to allocate a large enough buffer. This is
necessary for backward compatibility
Improved validation and prevention of overflow in maxSize argument.
Updated autotest that relied on a null QByteArray when no data was
available and no errors were found. The only guarantee we should be
providing in this case is an empty result -- even though that behavior
is preserved for the time being.
Affected functions:
* QIODevice::read(qint64 maxSize)
Chunking will still happen for large maxSize (i.e., QByteArray
resize fails), where it could be used as a synonym for
QIODevice::readAll().
No stat'ing performed. Read from device continues for as long as it
is successful. Stops if an error occurs or if we get less data than
requested.
* QIODevice::readAll()
Chunking is performed for sequential devices where total size
wouldn't be known beforehand. For sequential devices, reading
continues as long as data is returned, even if less than requested.
Non-sequential devices will be stat'ed once. If QIODevice::size
returns 0, this is taken to mean unknown size and chunking is
performed.
Otherwise, a single read request is made for the specified size. On
failure to resize QByteArray, nothing is returned.
* QIODevice::readLine(qint64 maxSize)
Chunking is performed for maxSize == 0, or if we can't allocate a
large enough buffer.
No stat'ing performed at this level. Read from device continues
until EOL is found, as long as we get all requested data.
Task-number: QT-2347
Reviewed-by: Thiago Macieira
Reviewed-by: Miikka Heikkinen
|
| |
| |
| |
| | |
... by catching failure to launch separate process earlier.
|
|/
|
|
|
|
|
|
|
|
|
| |
When writing nothing to a file, not actually writing anything is not an
error.
Also, from a change introduced in the same commit, there is no point in
checking for EOF when writing.
Task-number: QTBUG-5847
Reviewed-by: Olivier Goffart
|
|\ |
|