Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

[TEST] Multiple Users Reported Failing Tests #4927

Closed
3 of 4 tasks
ghost opened this issue Jul 30, 2018 · 5 comments
Closed
3 of 4 tasks

[TEST] Multiple Users Reported Failing Tests #4927

ghost opened this issue Jul 30, 2018 · 5 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Jul 30, 2018

Problem

Since around 2 months, multiple users were reporting test-failures.

List of Issues

Effective Root Cause

  • The CI Test-System does not use the same local tests. This way, the test-failures were not detected in an automated manner since months

Possible Causes

Own tests on an quite slow i7-16GB laptop show that the failures seem sporadic (not sure though)

  • possibly some test-timeouts end up in problems on slower machines
  • possibly a full clean-up (processes, data-dirs) is needed for some of the tests

Priority

This issue should get a quite high priority (similar to e.g. build-system-stabilization, like #4923)

Subtasks

(I am currently at this. Anyone can jump in and provide the logs, ideally as file attachments to this issue)

  • Find out if the failures occur always at the same tests: => no
  • Find out if the failures occur when test is run alone (ctest -R test-name): => sporadically
  • Produce test-logs: [TEST] Sporadic Failure, nodeos_voting_lr_test #5036 nodeos_voting_lr_test (last failing tests)
  • Get feedback from core-devs

Update

With version 1.1.3, test-errors have disappeared, except for #5036 nodeos_voting_lr_test (fix is in queue)

Full Test-Sequence

ubuntu 18.04, fresh install (Native, Virtual or WSL), then

sudo apt update
sudo apt upgrade
# fetch repo & submodules
./eosio_build.sh
# launch mongodb, as instructed
cd build
ctest --output-on-failure

(it seems apt update/upgrade is not deterministic, but ignoring for now)

@ghost
Copy link
Author

ghost commented Aug 5, 2018

The good news: test pass now (version 1.1.3), VirtualBox on Win10pro

The bad news: Total Test time (real) = 3557.49 sec - obviously, I need a new machine.

100% tests passed, 0 tests failed out of 41

Label Time Summary:
long_running_tests    = 1301.26 sec*proc (2 tests)

Total Test time (real) = 3557.49 sec

laz@laz-vb:~/eos/build$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic
laz@laz-vb:~/eos/build$ 

@jgiszczak
Copy link
Contributor

The long running tests will always take a considerable amount of time as they are dependent on wall clock time. Several of the tests not in the long running section are also dependent on real time.

@ghost
Copy link
Author

ghost commented Aug 7, 2018

Ah, I see. Thanks for clarifying.

(But I guess I'll need anyway a classy workstation to minimize build-times)

@ghost
Copy link
Author

ghost commented Aug 17, 2018

@brianjohnson5972 , can you please reopen #5036, as I'm still getting errors (1 of 5 runs) ?

@ghost
Copy link
Author

ghost commented Aug 22, 2018

Closing in favor of #5263

@ghost ghost closed this as completed Aug 22, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants