i said 5 minutes not 5%.

but sounds like an issue with your system, not the tasks. my tasks have never gotten stuck like that.

____________--

Chill, bro. Completed and validated.

It is 20 minutes on my hdd.

that makes sense for a slower device like a HDD.

---

Is the Python project dead ?

Is the Python project dead ?

Could be. Haven't seen the researcher behind those task types around for quite a while.
Could be he has moved on or maybe just taking a summer sabbatical or something.

Hi,

I'm receiving the following error message after about 700-800 sec running time:

09:33:09 (32292): Library/usr/bin/tar.exe exited; CPU time 0.000000
09:33:09 (32292): wrapper: running C:/Windows/system32/cmd.exe (/c call Scripts\activate.bat && Scripts\conda-unpack.exe && run.bat)
Could not find platform independent libraries <prefix>
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
  program name = '\\?\D:\ProgramData\BOINC\slots\4\python.exe'
  isolated = 0
  environment = 1
  user site = 1
  safe_path = 0
  import site = 1
  is in build tree = 0
  stdlib dir = 'D:\ProgramData\BOINC\slots\4\Lib'
  sys._base_executable = '\\\\?\\D:\\ProgramData\\BOINC\\slots\\4\\python.exe'
  sys.base_prefix = 'D:\\ProgramData\\BOINC\\slots\\4'
  sys.base_exec_prefix = 'D:\\ProgramData\\BOINC\\slots\\4'
  sys.platlibdir = 'DLLs'
  sys.executable = '\\\\?\\D:\\ProgramData\\BOINC\\slots\\4\\python.exe'
  sys.prefix = 'D:\\ProgramData\\BOINC\\slots\\4'
  sys.exec_prefix = 'D:\\ProgramData\\BOINC\\slots\\4'
  sys.path = [
    'D:\\ProgramData\\BOINC\\slots\\4\\python311.zip',
    'D:\\ProgramData\\BOINC\\slots\\4\\DLLs',
    'D:\\ProgramData\\BOINC\\slots\\4\\Lib',
    '\\\\?\\D:\\ProgramData\\BOINC\\slots\\4',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x000058b0 (most recent call first):
  <no Python frame>
09:33:10 (32292): C:/Windows/system32/cmd.exe exited; CPU time 0.000000
09:33:10 (32292): app exit status: 0x1
09:33:10 (32292): called boinc_finish(195)

Any idea why this error happens recently?

Thanks,

Peter

Hi,

I'm receiving the following error message after about 700-800 sec running time:
...
Any idea why this error happens recently?

when did you receive this task from which you think it's a Python? Pythons have not been around for quite a while - just take a look at the server status page

I think it's a python task because the error message is regarding a python problem:

Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

I got these tasks today and in the recent days:

Task received at in UTC | Computing status text | Runtime | Application name
28 Aug 2024 8:31:51 UTC | Error while computing | 672.11 | ATMML: Free energy with neural networks v1.01 (cuda1121)
28 Aug 2024 8:03:54 UTC | Error while computing | 703.63 | ATMML: Free energy with neural networks v1.01 (cuda1121)
28 Aug 2024 7:34:52 UTC	| Error while computing | 708.96 | ATMML: Free energy with neural networks v1.01 (cuda1121)
28 Aug 2024 7:20:30 UTC	| Error while computing | 714.93 | ATMML: Free energy with neural networks v1.01 (cuda1121)
28 Aug 2024 8:17:39 UTC	| Error while computing | 709.18 | ATMML: Free energy with neural networks v1.01 (cuda1121)
28 Aug 2024 7:49:20 UTC	| Error while computing | 724.49 | ATMML: Free energy with neural networks v1.01 (cuda1121)
27 Aug 2024 9:35:49 UTC	| Error while computing | 776.90 | ATMML: Free energy with neural networks v1.01 (cuda1121)
27 Aug 2024 1:24:00 UTC	| Error while computing | 60.60 | ATMML: Free energy with neural networks v1.01 (cuda1121)
26 Aug 2024 9:41:56 UTC	| Error while computing | 20.18 | ATMML: Free energy with neural networks v1.01 (cuda1121)

Those describe themselves as ATMML tasks - the clue is in the name.

There's been a major problem with ATMML tasks in the last 24 hours - all workunits created since around 13:00 UTC yesterday have a systemic failure which cause them to fail very early.

That's the project's problem, not your problem.

Thank you

Those describe themselves as ATMML tasks - the clue is in the name.

There's been a major problem with ATMML tasks in the last 24 hours - all workunits created since around 13:00 UTC yesterday have a systemic failure which cause them to fail very early.

That's the project's problem, not your problem.