Open anjalirai-intel opened 3 years ago
@anjalirx-intel @jinengandhi-intel Have you re-tried this test again after we agreed to update Stress-ng version? See discussion in https://github.com/oscarlab/graphene/issues/2419#issuecomment-878004114.
Dmitrii, we had agreed that the 2419 issue could be related to the stress-ng version, wasn't asked to test the chmod test. For latest version of stress-ng we need to try out on an Ubuntu 20.04, which we haven't been able to.
My assumption is that the new stress-ng version may fix this issue (since it looks related to the root cause of #2419). Anyway, assigning P1 for now and hope this will be trivially resolved when moving to the new stress-ng version.
Verified on below config as said. Issue still exists.
Error: graphene-direct stress-ng --chmod 3 --timeout 60s
error: Using insecure argv source. Graphene will continue application execution, but this configuration must not be used in production!
error: Forwarding host environment variables to the app is enabled. Graphene will continue application execution, but this configuration must not be used in production!
[P372046:T1:] error: 'libos.entrypoint' is now a Graphene path, not URI. Ignoring the 'file:' prefix.
stress-ng: info: [1] dispatching hogs: 3 chmod
stress-ng: fail: [3] stress-ng-chmod: fchmod failed, errno=2 (No such file or directory)
stress-ng: info: [1] successful run completed in 60.05s (1 min, 0.05 secs)
Machine Config: Kernel 5.12.0-051200-generic OS: 20.04.1 LTS (Focal Fossa) Stress-ng: version 0.11.07 (gcc 9.3, x86_64 Linux 5.12.0-051200-generic)
stress-ng: fail: [3] stress-ng-chmod: fchmod failed, errno=2 (No such file or directory)
This looks like just a missing entry in the manifest. Could you run this on "trace" debug level and find on which file it fails?
@mkow This is not about missing file in the manifest. If you see the above observation mentioned in description, initially it worked for 1 stressor and 3 stressor as well and then it throw No such file or directory error
Hmm, but still, this info would be very helpful to see why it could fail.
Closed the issue by mistake
Partial Logs chmod_4_stressor_trace.zip
Complete Logs is not able to upload because file size is too high even after compressing.
Description of the problem
As no of stressors increased per CPU, chmod calls fails with graphene-direct
Run-1:
Run-2:
Run-3:
Run-4: