Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRG object have no output when running makei b #328

Open
irfanshar opened this issue Jun 26, 2024 · 5 comments
Open

TRG object have no output when running makei b #328

irfanshar opened this issue Jun 26, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@irfanshar
Copy link
Collaborator

For our CL pseudo source, we expect output like the following

=== Creating BND from [SAMPLE.BNDDIR]
!DLTOBJ OBJ(bobirfan/SAMPLE) OBJTYPE(*BNDDIR)
CRTBNDDIR BNDDIR(bobirfan/SAMPLE)
 ADDBNDDIRE BNDDIR(bobirfan/SAMPLE)  OBJ((*LIBL/XML *SRVPGM) (*LIBL/ORDER *SRVPGM) (*LIBL/TXT *SRVPGM)  (*LIBL/XSS *SRVPGM) (*LIBL/FARTICLE *SRVPGM)  (*LIBL/FCUSTOMER *SRVPGM) (*LIBL/FFAMILLY *SRVPGM)  (*LIBL/FPARAMETER *SRVPGM) (*LIBL/FPROVIDER *SRVPGM) (*LIBL/FVAT *SRVPGM) (*LIBL/LOG *SRVPGM))

✓ SAMPLE.BNDDIR was created successfully!

We don't see that for TRG objects.

@edmundreinhardt does this have to do with the fact that these files use ADDPFTRG instead of CRTxxx like our other CL pseudo-source

@irfanshar irfanshar added the bug Something isn't working label Jun 26, 2024
@edmundreinhardt
Copy link
Member

It seems to fail at irregulat times

Running Action: /QOpenSys/pkgs/bin/makei build (4:11:23 PM)
Working directory: /home/REINHARD/builds/bob-recursive-example
Commands:
	/QOpenSys/pkgs/bin/makei build

> /QOpenSys/pkgs/bin/make -k BUILDVARSMKPATH="/tmp/tmph6pebp52" -k BOB="/QOpenSys/pkgs/lib/bob" -f "/QOpenSys/pkgs/lib/bob/src/mk/Makefile" all
make: Warning: File '/home/REINHARD/builds/bob-recursive-example/QSQLSRC/ORD701.SQLTRG' has modification time 14091 s in the future
=== Creating SQL TRIGGER in from Sql statement [ORD701.SQLTRG]
RUNSQLSTM srcstmf('/home/REINHARD/builds/bob-recursive-example/QSQLSRC/ORD701.SQLTRG') DBGVIEW(*SOURCE) TGTRLS() OUTPUT(*PRINT) MARGINS(1024) COMMIT(*NONE )
/QOpenSys/pkgs/bin/bash: line 1: /home/REINHARD/builds/bob-recursive-example/.logs/ORD701.splf: No such file or directory
✕ Failed to create ORD701.PGM!

make: warning:  Clock skew detected.  Your build may be incomplete.
Objects:             1 failed 0 succeed 1 total
 > Failed objects:    ORD701.PGM
Build Completed!

Fetching errors from .evfevent.
Failed to download a file after Action: No such file

What I notice is that

  1. there is a time skew on p8adt05 that makes BOB this that this source is new when it is not
    make: Warning: File '/home/REINHARD/builds/bob-recursive-example/QSQLSRC/ORD701.SQLTRG' has modification time 14091 s in the future
  2. At random times we get the message
    /QOpenSys/pkgs/bin/bash: line 1: /home/REINHARD/builds/bob-recursive-example/.logs/ORD701.splf: No such file or directory

The problem occurs for both BUild and Compile modes
The second message does not appear when it succeeds

@edmundreinhardt
Copy link
Member

That message is happening when the standard out is being written to the output at

$(SCRIPTSPATH)/launch "$(JOBLOGFILE)" "$(crtcmd)" "$(PRECMD)" "$(POSTCMD)" "$(notdir $@)" "$<" "$(logFile)" "" "$(mbrtextcmd)"> $(logFile) 2>&1 && $(call logSuccess,$@) || $(call logFail,$@)

The problem is that somebody deleted the ".logs" directory and then didn't recreate it.
Please investigate this.
@irfanshar

@irfanshar
Copy link
Collaborator Author

@edmundreinhardt What steps can I take to reproduce this?

I am not seeing the original issue anymore (where there is no output when running makei b).

I also am not seeing the message /QOpenSys/pkgs/bin/bash: line 1: /home/REINHARD/builds/bob-recursive-example/.logs/ORD701.splf: No such file or directory that you get randomly, after attempting to build the object multiple times.

I have attempted both build and compile modes.

I also manually removed the .logs directory and then tried to build and still did not see the message

@AIforIBMi
Copy link
Collaborator

As discussed, let's modify the extensions to NOT delete .evfevent and .logs

@irfanshar
Copy link
Collaborator Author

Modification to clear .evfevent and .logs is being tracked here IBM/vscode-ibmi-projectexplorer#538

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants